Troubleshooting

This section provides troubleshooting tips:

Problem 1

Installation Failure due to Insufficient Space

Analysis

The setup fails because the space in the target drive is not sufficient.

Solution

The setup reports the required space in the installation GUI. Ensure that at least twice the reported space is available. The extra space is required for decompression operation.

Problem 2

While installing iPSI CLI Verify Tool, some invalid characters appear in the installation path. The installer does not validate the path and  iPSI CLI Verify Tool gets installed in some other path.

Analysis

The installer takes the given installation path.

Solution

Remove the invalid characters such as ; , % from the given path. If the new path is valid, then iPSI CLI Verify  Tool will get installed in the new path.

Problem 3

When executing ipsi_verify_tool.exe, an error occurs - "ErrorCode: 25018 Config XML Error: Xml Validation Failed"

Analysis

 The installation path contains unicode or UTF characters (Chinese) which is not supported by the tool.

Solution

 iPSI Sign Verify Tool installation path must not contain unicode/UTF characters.

Problem 4

While installing and uninstalling iPSI CLI Verify Tool, the close button does not work.

Analysis

Figure

Solution

This does not affect the functionality of the system.

Problem 5

 When we try to run the CLI Verify tool, it always gives an error as "An instance of the tool is already running", even if no instance of the tool is running in the system.

Analysis

 At any point of time only one instance of  CLI Verify tool is allowed to run. In case of Linux/Solaris CLI, the user gets this error if the process is killed or the session gets closed abruptly.

Solution

 In case of Linux/Solaris CLI Verify tools, there is a command called "close_ipsi_verify" to overcome this error. But the usage of this command is strictly not recommended unless until it is really required. The user should not use this command to work simultaneously in different sessions,  the result is unpredictable. If the user is facing this problem since long time and he is sure that, there is no other operation running in any other sessions, he can use this command.

Problem 6

Log related error code and reason are displaying even on success of the operation:

Analysis

This is because of a log file creation failure. It does not affect the tool verification operation. It just displays an error and continues with operation.

Solution

If user does not want to show this error caused by the Log file creation failure, disable the log in XML file. To disable the Application log , set the AppLogFlag as No. To disable the Debug log, set the DbgLogFlag as No.

Problem 7

When executing ipsi_verify_tool on Windows, the following error occurs:

ErrorCode: 26201 Log Error: Setting Application Log Failed or

ErrorCode: 26202 Log Error: Setting Debug Log Failed

Analysis

 This is due to Windows not allowing the ipsign tool to write to the log file because of inadequate file permissions.

Solution

Start the command prompt with Administrator rights using the Run as administrator option. To do this, right-click on the Command prompt and select Run as administrator.